[FEAT]: Update safhandle description - #9
Conversation
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters (1)
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
📝 WalkthroughWalkthroughThis PR updates SafHandle metadata in the app manifest and registry, including naming, descriptions, beta status, links, tags, language metadata, version, and timestamps. ChangesSafHandle App and Registry Metadata Update
Estimated code review effort: 1 (Trivial) | ~5 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Hey @Mechack08 |
Summary
Update the existing SafHandle listing (
apps/safhandle/) so it accuratelydescribes the SafHandle web dApp. The entry previously described the SDK and sat
in
conceptstatus.name,shortDescription, anddescriptionto the app's real,code-verified features:
.safname (3–32 chars,a–z 0–9 -, one per wallet);transfer or release it (
register_name/transfer_name/release_name).addr_safro…address and reverse-lookup — free, read-only,no account or fee (
get_address/resolve_name/handles).exact on-chain fee read from contract config.
status:concept→betawith a testnetstatusNote(live on
safro-testnet-1; mainnet contract pending).url→ live app https://handle.safrochain.com.links:website(app),github(open-source SafHandle SDK), anddocs→ the SafHandle SDK on npm. (Thelinksschema has nosdkkey —additionalProperties: false— so the SDK link lives underdocs.)version(0.1.0),languages(en), app-focusedtags, and setupdatedAt.registry.json.Checklist (required)
npm ciandnpm run validatelocally — it passed before opening this PR.npm run build:registryand committed the updatedregistry.jsonin this PR.apps/<slug>/withjson/app.jsonandimg/logo.png.<slug>is 2–64 chars, lowercase letters and digits only (no spaces or hyphens), andslugin JSON matches the folder name.npm run validate)Validation output (paste if useful)
```
Validation OK.
```
Summary by CodeRabbit
New Features
Updates